LOYALTY RELEASE 26.2.0

 

Dashboard Exports Now Preserve your Applied Filters

Available to all CLIENTS

Background

Previously, Dashboard exports reverted to default filters regardless of what you had applied, creating inconsistent results. Dashboard exports and scheduled reports now capture and apply the exact filters you set at the time of export, ensuring the data you see is the data you send.

Solution

When you export a Dashboard or schedule a report, the platform preserves your active filter state and applies it consistently across all executions.

You can now distribute filtered reports with confidence, knowing that stakeholders receive exactly the data you intended. Whether you're sharing member segmentation analysis, campaign performance metrics, or compliance reports, your exports reflect the specific view you configured.

What it looks like in Loyalty

When exporting or scheduling a Dashboard, you'll see a simple checkbox that lets you choose between using your current active filters or the Dashboard defaults. Your selection is saved with the export configuration and applied every time the report runs, giving you full control over the data your stakeholders receive. This enhancement applies to both immediate exports (Email Now) and recurring schedules (Email Regularly) across all supported export formats, including PDF, PNG, and CSV.

This feature provides the following key benefits:

• Accuracy and consistency: The filters you apply are the filters that get used, eliminating unexpected results.

• Clear control: Choose between current active filters or defaults with a single, straightforward checkbox.

• Time savings: No need to manually verify or adjust exports after the fact.

• Protected defaults: Dashboard default filters remain unchanged, preventing unintended modifications.

For more information on Dashboards, see Dashboards.

 

Expiration Period Override for Last Activity Expiration Policy

Available to all CLIENTS

Background

By default, the Last Activity Metric expiration will expire a Member’s balance after a specified period of inactivity. It is now possible to configure overrides to the default expiration period, in order to support different expiration periods for qualifying Members.

Solution

This feature allows programs to define overrides to the default expiration period to support one or more context-specific expiration periods for Members that match the override condition.

For example, an override could specify a locale or region a Member is part of to allow the system to expire points in a different period of time for those specified locations. For all Members that don’t match the override condition, the system would use the expiration period defined in the policy configuration. Conversely, for Members that match an override condition, the system would use the period specified in the override. Let's say a program has a default expiration period of 6 months, and has an override that applies a 12-month expiration for members who signed up in Canada. As the system processes Activities, it will apply a 12-month expiration to Members who signed up in Canada, and 6 months for all other Members.

Note: The expiration period override is available only for the Last Activity type expiration policy; it is not available for programs using Every Activity or Program Date expiration policy types.

What it looks like in Loyalty

This capability allows you to operate a unified loyalty program that adapts to the distinct requirements of your Member base, ensuring both regulatory adherence and operational efficiency.

This feature provides the following key benefits:

• Maintain compliance across jurisdictions: Meet varying regulatory requirements by extending expiration periods for specific regions or Member groups without compromising your core program structure.

• Preserve program consistency: Keep your standard expiration policy intact while accommodating necessary exceptions, ensuring a cohesive Member experience.

• Configure conditions without code: Use an intuitive condition builder to define when expiration extensions apply, eliminating the need for custom scripting or technical implementation.

• Control expiration logic with clarity: Set interval periods and values, build conditions based on Member context, and manage multiple conditions in sequence, all through straightforward configuration.

For more information, see the Point Expiration User Guide.

 

Require Country Code for Mobile Numbers

Available to all CLIENTS

Background

We renamed the Required mobile phone validation Program Setting to Require country code for mobile numbers, and updated its description to clarify functionality.

Solution

This change to the Program Setting name and description eliminates confusion for users by providing a clearer understanding of how the setting controls mobile number validation in the Program API.

What it looks like in Loyalty

This update improves clarity and reduces misunderstandings during configuration and implementation by providing the following changes:

• Setting name: New name accurately reflect its purpose.

• Setting description: Updated the description to state that when enabled, Program API Member create/update requests must include a mobile number with a country code or validation fails. When disabled (default), the system resolves the country code, normalizes the number, and saves it.

For more information, see Program Settings.

 

Test Member Count Now Requires Saved Rule Conditions

Available to all CLIENTS

Background

We refined how the Test Member Count button works in Golden Record-type Segments to ensure your Member counts reflect intentional, saved rule configurations.

Solution

The Test Member Count button is now disabled when rule conditions have not been saved. This functionality prevents the system from counting Members against incomplete or unsaved configurations, eliminating confusion about which rules are being evaluated.

What it looks like in Loyalty

When you create a new Golden Record-type Segment without saving any rule conditions, or when you modify existing rules without saving your changes, the Test Member Count button becomes unavailable. This functionality ensures that every Member count calculation reflects the exact rule set you intended to test.

This feature provides the following key benefits:

• Eliminate ambiguity: Know with certainty that your Member counts correspond to the saved rule conditions you're reviewing, not an unknown or incomplete configuration.

• Prevent unintended calculations: Avoid running Member counts against empty or unsaved rule sets, which could produce misleading results.

• Support intentional testing: Ensure every test reflects a deliberate decision to evaluate specific Segment criteria.

This enhancement gives you confidence that your Segment analysis is based on the rules you've explicitly defined and saved.

For more information, see Segment Details - Rules.

 

Updated Phone Validation Support

Available to all CLIENTS

Background

We’ve updated the phone validation module in this release to align with recent changes in acceptable international phone formats with the intent to deliver more accurate and comprehensive global phone validation behavior.

 

Resolved Issues

Bug Fixes

• Annual Metric expiration batch jobs now complete successfully. We fixed an analytics engine error that aborted jobs for program-date expiration configurations.

• Import success notifications now deliver as configured. We fixed a metadata issue that prevented success email notifications from being sent to designated recipients during import operations.

• Badge API now respects Segment eligibility. We fixed an issue where the Get Badges API returned all Badges instead of only those allowed by Segment configuration.

• Role deletion now works as designed. We fixed an issue that prevented administrators from deleting custom roles with no assigned users.

• Member Metric balances now display accurately. We corrected calculation errors that caused incorrect Metric balances, including negative balances and issues related to program Metric changes that displayed outdated expiration dates in the platform interface, as well as historical timestamp processing bugs from closely sequenced redemption activities.

• Offer Response imports now process updates with flexible field matching. We corrected an issue that blocked Offer Response updates when member_id and offer_id were included in field mappings, allowing you to match records by alternative fields as configured.

• Export jobs handle Segment status checks without errors. Fixed an issue where export jobs linked to Segments failed with a "None.get" error when the Segment task had never completed successfully.

• Challenge display tab now handles template configurations reliably. Addressed an issue where accessing the Display tab on new Challenges resulted in errors when master content template files were missing or invalid.

See Loyalty Upcoming Releases for the platform release schedule.

See System Maintenance for details on the next system maintenance window, per region.

The status page provides you with regular updates regarding the status of the Loyaltyplatform in the event of a major system incident in your region. In this article we’ll explain the information you will see and how to subscribe to the Loyalty notification system to receive regular updates on the platform status, which we highly recommend to all users.

See Platform Status for more details.